-
Couldn't load subscription status.
- Fork 25.6k
[ML] Increase default queue_capacity to 10_000 and decrease max queue_capacity to 100_000 #115041
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Pinging @elastic/ml-core (Team:ML) |
|
Hi @maxhniebergall, I've created a changelog YAML for you. |
…icsearch into trainedModelsQueueCapacity
…odelsQueueCapacity
💔 Backport failedThe backport operation could not be completed due to the following error: You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…_capacity to 100_000 (elastic#115041) * Increase default queue capacity and decrease max queue capacity * Update docs/changelog/115041.yaml * Update tests to match new constants
…_capacity to 100_000 (elastic#115041) * Increase default queue capacity and decrease max queue capacity * Update docs/changelog/115041.yaml * Update tests to match new constants
…_capacity to 100_000 (elastic#115041) * Increase default queue capacity and decrease max queue capacity * Update docs/changelog/115041.yaml * Update tests to match new constants
Updating with changes in elastic#115041
Updating with changes in elastic#115041
…tic#118891) Updating with changes in elastic#115041
The default queue_capacity of 1024 has been affecting some customers who experience errors during reindex or when using ingest pipelines. Now that we have automatic chunking, this issue is more common. To prevent customers from running into this issue, we are increasing the default queue_capacity to 10'000. At the same time, we have found that the previous maximum queue_capacity of 1MM was too large, and would cause crashes if filled. We are decreasing it to what we believe is a more realistic value.
The queue_capacity of existing deployments should be unaffected by this change.